Skip to content

docs(process): explain our integration automated checks; revamp navigation #2764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 13, 2023

Conversation

heitorlessa
Copy link
Contributor

@heitorlessa heitorlessa commented Jul 13, 2023

Issue number: #2203

Summary

Expands our soon-to-be-released Process docs section to explain our automated checks before, during, and after each contribution.

PS: I'll do CD in another month as it'd take a whole day to document at this level of detail.

Changes

Please provide a summary of what's being changed

  • Explain CI automated checks along with links to workflows etc
  • Expanded documentation to use Tabs as we reached the limit in screen real estate
  • Move CI/CD automation details in /security to /automation
  • Created new Process docs section and split CI/CD from Security into Automation page
  • Migrated Maintainer's playbook to user guide
  • Expanded installation to suggest our new signed release builds
  • Added tooltip to Lambda Layer for new customers not understanding what '{region}' means.

User experience

Please share what the user experience looks like before and after this change

New look with tabs

image

New process section

image

Checklist

If your change doesn't seem to apply, please leave them unchecked.

Is this a breaking change?

RFC issue number:

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

@heitorlessa heitorlessa requested a review from a team July 13, 2023 08:59
@boring-cyborg boring-cyborg bot added the documentation Improvements or additions to documentation label Jul 13, 2023
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 13, 2023
@heitorlessa heitorlessa changed the title docs(security): explain our integration automated checks docs(process): explain our integration automated checks; revamp navigation Jul 13, 2023
@pull-request-size pull-request-size bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 13, 2023
@boring-cyborg boring-cyborg bot added the internal Maintenance changes label Jul 13, 2023
@pull-request-size pull-request-size bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 13, 2023
@github-actions
Copy link
Contributor

⚠️Large PR detected⚠️

Please consider breaking into smaller PRs to avoid significant review delays. Ignore if this PR has naturally grown to this size after reviews.

1 similar comment
@github-actions
Copy link
Contributor

⚠️Large PR detected⚠️

Please consider breaking into smaller PRs to avoid significant review delays. Ignore if this PR has naturally grown to this size after reviews.

@heitorlessa heitorlessa requested a review from rubenfonseca July 13, 2023 13:18
@heitorlessa heitorlessa merged commit 8625ccb into aws-powertools:develop Jul 13, 2023
@heitorlessa heitorlessa deleted the docs/security branch July 13, 2023 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation internal Maintenance changes size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants